Let's talk about how to get ready for an interview. So before you even get to the interview, you can read the job description. And I think a really important question to ask yourself and try to guess based on the job description is, do they have a specific role that they're trying to fill or replace here? Is it more like they're growing a team and they need many different people to staff up their team? Or are they hiring because they have a really specific problem and they need expertise to be able to solve it? These all might look really different. For example, if someone is growing a team, they might have jobs descriptions for multiple levels of the same role and or multiple locations. And if there's a very specific problem, you might have come across the job description through networking because people know about your history. So when you get to the interview, and here I'm going to focus really on SQL skills, there's a whole lot of things that sit within the realm of just coding. So understanding basic SQL syntax, getting through the problem solving, overcoming errors, even as far as optimizing query performance, which could be part of a more data engineering focused role. And then there are also opportunities to showcase your skills like domain knowledge, making sure that they know if you know something already about the business domain or that you show real interest in learning. And then of course, every question, every opportunity to communicate is a place to show off your communication skills. There are a spectrum of questions that could go from very specific to open ended. And I find when interviewing people that it's very common for people to assume that the question is always specific, meaning it tests a very specific skill and concept. And that the goal is to demonstrate speed and confidence. And that there's exactly one right answer. And an example of a question like this might be, what's the max value in this column? That is a very specific skill. And you would want to demonstrate speed and confidence here. But there are a lot of questions in interviews that are also open ended. They test your creativity, your problem solving, they really get to look into your mind and see how you break down a big ambiguous problem. And it is your opportunity to clarify, articulate, communicate, figure out what the shared goals are so that you can come up with a really good strategy for solving the problem in potentially multiple ways. And an example might be, how would you identify the most valuable customer type? Then of course, there's different question formats, especially for SQL interviews. The most common would be live coding or a whiteboard. In a live coding environment, you're going to have the opportunity to run your code in the environment against a real data set. And when you do that, there's an opportunity to show that you can overcome bugs and errors and to demonstrate your mastery of specific dialects. Whereas on a whiteboard, you're not really developing code that needs to run. It's a draft of a solution. So a missing comma is probably not going to make or break it for you. What you're showing off is your problem solving skills, as well as your communication. And the evaluation of the solution here is really just based on the structure and the logic. So I'm curious to hear in the discussion, what kind of SQL interview questions have you gotten if you've been interviewing? And what formats do you struggle with? And then I'll leave you with an invitation to practice. We will have a document here with a whole bunch of sample questions that you can practice on with our class data set. And I invite you to think about how you would answer these differently if you assumed that they were a specific question versus an open-ended question. If you were answering them on a whiteboard versus in a live coding environment. This is your chance to get as much practice as you need to feel comfortable and ready for an interview.